Separated this into a dedicated function, removed recursion and removed the closure. I removed the closure because it's annoying to deal with move semantics in the closure - particularly as we refactor the request tracker approach in the future.

This is more a concern for the binding layer rather than of the AssetGraph itself. Extracted it into a function, should probably move it into node_bindings

We have a lot of serialisation baked into the core types already, but it can go in either location 🤷

Trying to keep this data structure focused on being a holder of data and minimize manipulation of that data in methods.

Essentially, this is just a graph with add/get methods, consumers decide what to do with the data so the details of manipulations to the data live at the call site

The AssetGraph looks like:

root -> (n) dependency -> (n) asset (entry)

This will walk the graph and find the first asset which should be the entry asset